Overview
Custom Terminologies are replaceable terms which are customisable on a per-customer basis. In practical situations, this means the term "store_region" may be shown as "Store Region" at one customer site, and as "Store Province" at another site. Maintain Custom Terminologies allows the user to edit the terms and the human readable names they resolve to.
Additional Information
The Maintain Custom Terminology application contains the following fields:
Field | Description |
Code | The custom terminology code. This needs to be all lowercase, with words separated by underscores. Eg. store_sub_region. |
Custom Name | The human readable name which will appear on forms and reports instead of the codename. |
Format | In the case of reports, columns can be formatted with a default format string if their heading matches a custom term. For example, a customer can have a default sale_value custom term which specifies #,##0.00 as its format string, meaning all Sale Value columns will have cents in their format. |
Notes | Contains notes explaining the usage and purpose of the custom term, if necessary. |
Child Terminologies
Custom Terminologies may be extended using child terminologies. For instance, a sale_value_day custom term may exist, and it might have children called _mon, _tue, _wed and so forth. The following columns are shown in the Child Terminology grid:
Field | Description |
Code Name Suffix | This contains the suffix of the code. For instance, if the parent term was called "sale_value" and the child is called "monday", the full custom term name would be "sale_value_monday". This conjoined name is used when custom terms are resolved to human readable terms. |
Custom Name | Refer to the Custom Name column above. |
Format | Refer to the parent format column above. |
Notes | Refer to the notes column above. |
See Also